scarb & snforge upgrade #2570
scarb & snforge upgrade #2570
Conversation
|
@iossocket is attempting to deploy a commit to the Pyth Network Team on Vercel. A member of the Team first needs to authorize it. |
|
Looks good! Can you please fix the CI issues? I think you need to bump the rust toolchain version in |
|
@Riateche Thanks for your reviewing, have updated the pr, looks like the CI would not be triggered automatically, pending review |
|
Hi @Riateche, I have replaced the dojo with starknet-devnet, and verified the workflow on my forked https://github.com/iossocket/pyth-crosschain/actions |
|
|
||
| 1. Install Starkli (a cli tool for Starknet) by following [the installation instructions](https://github.com/xJonathanLEI/starkli). | ||
| 2. Install Katana (a local Starknet node) by following [the installation instructions](https://book.starknet.io/ch02-04-katana.html). | ||
| 2. Install Devnet (a local Starknet node) by following [the installation instructions](https://book.starknet.io/ch02-04-katana.html). |
There was a problem hiding this comment.
Can you please update the link to the installation instructions as well?
2 participants
Summary
We are working on a lending protocol that integrates pyth on Starknet and would like to use the latest versions of snforge and scarb.
Rationale
Getting conflicts when using the latest scarb.
How has this been tested?
No logic change, update the dependencies(openzeppelin, snforge_std), change some syntax in unit tests caused by snforge break changes.